Icon

[03.CX] Extracting and Transforming Viber Broadcast Data from Infobip

Extracting & Transforming ViberBroadcast Data from Infobip 1) Context: Infobip is a leading provider of omnichannelcommunication, contact center, chatbot, customerengagement, and customer data platforms. Leveragingthis cutting-edge technology, we share farming practicecontent with farmers via Viber on their smartphones. Toensure data safety and security, we transfer the data usingSFTP, as recommended by Infobip. Then, we fetch thisdata and use it in our ETL pipeline for reporting purposes 2) Context: A senior management member has made a last-minute request tomodify the naming on the dashboard, which serves as the front-end for all thebacked-end processes. This approach is not recommended as it is not future-proof.To address this, I need to collaborate with the backend team. I believe this presentsan opportunity for business-side individuals to enhance their understanding ofsystem designs and engineering. By doing so, we can foster better collaborationbetween system and business personnel and work towards a common goal. Restructured naming convention of OLD legacy systems to align withCURRENT naming convention across ALL the reporting & operation systemsCleaned Data for PBIDashboardAgent ListLast-minute requeston Naming Structure GoogleAuthentication Google SheetsConnection Viber ConversationExport Files Google SheetsReader Joiner Rule-basedRow Splitter Rule-basedRow Splitter Joiner Concatenate Excel Writer Concatenate Serives Products Table Creator Joiner DuplicateRow Filter Rule Engine Data Transformation Data Transformation Extracting & Transforming ViberBroadcast Data from Infobip 1) Context: Infobip is a leading provider of omnichannelcommunication, contact center, chatbot, customerengagement, and customer data platforms. Leveragingthis cutting-edge technology, we share farming practicecontent with farmers via Viber on their smartphones. Toensure data safety and security, we transfer the data usingSFTP, as recommended by Infobip. Then, we fetch thisdata and use it in our ETL pipeline for reporting purposes 2) Context: A senior management member has made a last-minute request tomodify the naming on the dashboard, which serves as the front-end for all thebacked-end processes. This approach is not recommended as it is not future-proof.To address this, I need to collaborate with the backend team. I believe this presentsan opportunity for business-side individuals to enhance their understanding ofsystem designs and engineering. By doing so, we can foster better collaborationbetween system and business personnel and work towards a common goal. Restructured naming convention of OLD legacy systems to align withCURRENT naming convention across ALL the reporting & operation systemsCleaned Data for PBIDashboardAgent ListLast-minute requeston Naming Structure GoogleAuthentication Google SheetsConnection Viber ConversationExport Files Google SheetsReader Joiner Rule-basedRow Splitter Rule-basedRow Splitter Joiner Concatenate Excel Writer Concatenate Serives Products Table Creator Joiner DuplicateRow Filter Rule Engine Data Transformation Data Transformation

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: Data Analytics Team
Created at: 2023-04-16
On NodePit since: 2023-04-17
Last update: 2024-04-27
Created with KNIME version: v4.5.2

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!